Method and system of subsetting a cluster of servers

ABSTRACT

A method and system of subsetting a group of server systems configures a server system with a group name and a group port, and with at least one subset name and subset port. The server system, when activated, reads its configuration and registers with a system routing entity as being part of the group name and the group port, and as being part of the subset name and the subset port. In this manner, server systems can be targeted via its subset name and subset port, while also accessible via the common name and port for the group. If the group includes a workload balancer, the server system also registers with the workload balancer using the group name and the subset name, such that workload balancing is provided for the subset.

FIELD OF THE INVENTION

The present invention relates to server systems, and more particularly to the subsetting of a cluster of server systems.

BACKGROUND OF THE INVENTION

Many techniques exist to “cluster” systems of servers for databases, web applications, etc., where the group of server systems is treated as a single entity. FIG. 1 illustrates a conventional group of server systems representing a single entity. A plurality of server systems 103.1-103.n is configured as a single group 101. From the perspective of a client 102, the group 101 of servers constitutes a single database or entity. When the client 102 wants to connect to one of the server systems 103.1-103.n of the group 101, any of the server systems 103.1-103.n are candidates for the client connection.

Occasionally, users of such systems wish to be able to automatically target a subset of the server systems 103.1-103.n so that only those server systems are affected by a particular set of client application requests. In one conventional solution, the client 102 requests a TCP/IP address for the server systems in the subset from a domain name server (DNS) (not shown). The DNS would be set up with lists that provide the server system TCP/IP addresses for a particular name, through which the subset of server systems can be accessed.

However, this solution has several drawbacks. First, for a typical DNS, the TCP/IP addresses of the server systems 103.1-103.n are given out to the client 102 in a round-robin manner without regard to whether or not the particular server system at the address is available and/or the server system has the capability to handle the client application's request. Second, once connected to the particular server system, the connection remains with that server system until a request to disconnect is received, without regard to whether or not the server system had the capacity to continue processing the client application's requests. This solution assumes that the client 102 disregards any server capacity feedback mechanisms. Third, if the client 102 did utilize the server capacity feedback mechanisms for workload balancing, the only information being returned from the server system would be capacity information for the group 101 as a whole, not just the subset of server systems. Eventually, requests would be sent to all server systems 103.1-103.n in the group 101.

In another solution, each server system of a subset would be defined with a unique “target” name that would be different from the name of the group 101, and probably have different TCP/IP access port numbers as well. This would permit the server feedback mechanisms to only report on the server systems of the subset. However, when a client application wants to access any or all of the server systems 103.1-103.n of the group 101, since there is no longer a common name for all of the server systems 103.1-103.n, there is no way for the client application to be able to get to any and all of the server systems 103.1-103.n in the group 101, unless the client application itself manages this aspect of the connection. In addition, any one server system can only participate in one and only one subset.

In both solutions, the sharing of data between the server systems in the group 101 is always a requirement whether a subset of the group of servers or the group as a whole is to be accessed.

Accordingly, there exists a need for an improved method and system of subsetting a group of server systems. This improved method and system should allow for a subset of server systems to be targeted by a client application, while preserving the direct data sharing capabilities between the subset of server systems and the remaining server systems of the group. In addition, the improved method should allow for load balancing and/or fault protection within a subset of server systems. The present invention addresses such a need.

SUMMARY OF THE INVENTION

A method and system of subsetting a group of server systems configures a server system with a group name and group port, and with at least one subset name and subset port. The server system, when activated, reads its configuration and registers with a system routing entity as being part of the group and the group port, and as being part of the subset name and the subset port. In this manner, server systems can be targeted via its subset name and subset port, while also accessible via the common name and port for the group. If the group includes a workload balancer, the server system also registers with the workload balancer using the group name and the subset name, such that workload balancing is provided for the subset.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a conventional group of server systems representing a single entity.

FIG. 2 illustrates an embodiment of a subsetting of a group of server systems in accordance with the present invention.

FIG. 3 is a flowchart illustrating an embodiment of the activation of subsetting a group of server systems in accordance with the present invention.

FIG. 4 is a flowchart illustrating an embodiment of establishing an initial connection with a server system of a subset in a group of server systems in accordance with the present invention.

DETAILED DESCRIPTION

The present invention provides an improved method and system of subsetting a group of server systems. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.

To more particularly describe the features of the present invention, please refer to FIGS. 2 through 4 in conjunction with the discussion below.

FIG. 2 illustrates an embodiment of a subsetting of a group of server systems in accordance with the present invention. A plurality of server systems 203.1-203.6 is configured as being part of a group or cluster 201, with a group name and a group port. Although six server systems are illustrated, any number of server systems can be used. In addition to being defined as a part of the group 201, each server system 203.1-203.6 can also be defined as part of one or more subsets, with each subset having a subset name and a subset port. For example, assume that the server systems 203.1-203.6 are defined as part of the group 201 named “group1” with port “9000”. In addition, servers systems 203.1 and 203.2 are defined as being part of a first subset 204 named “appgroup2” with port “9010”. The same is true for servers systems 203.5 and 203.6, which are defined as being part of a second subset 205 named “appgroup3” with port “9020”, as well as being part of “group1” 201. In this manner, server systems can be targeted via its subset name and subset port, while also accessible via the common name and port for the group 201. Work can be targeted to certain subsetted server systems, while the direct sharing of data between the server systems 203.1-203.6 of the group 201 is maintained.

FIG. 3 is a flowchart illustrating an embodiment of the activation of subsetting a group of server systems in accordance with the present invention. First, a server system is configured with a group name and a group port, and with a subset name and a subset port, via step 301. Next, the server system is started, via step 302. The server system reads its configuration, via step 303. It then registers with a system routing facility or table (not shown) as being part of the group name and the group port, via step 304. The server system also registers with the system routing facility or table as part of the subset name and the subset port, via step 305. The server system then listens for connections on both the group port and the subset port, via step 306.

For example, the server system 203.1 is configured with the group name “group1” and the group port “9000”, and with the subset name “appgroup2” and a subset port “9010”, via step 301. When the server system 203.1 is started, via step 302, it reads its configuration, via step 303. The server system 203.1 then registers with the system routing facility or table as part of the “group1” group 201 with port “9000”, via step 304. The server system 203.1 also registers with the system routing facility or table as part of the “appgroup2” subset 204 with port “9010”, via step 305. Once registered, the server system 203.1 listens for connections on ports 9000 and 9010, via step 306.

Once the group and its subsets are activated, a client application can connect to any of the server systems 203.1-203.6 as part of the group 201, or target a connection to a server system as part of a subset. FIG. 4 is a flowchart illustrating an embodiment of establishing an initial connection with a server system of a subset in a group of server systems in accordance with the present invention. First, the client 202 obtains the IP addresses for the system servers of the subset, via step 401. For example, a domain name server (DNS) (not shown) can be used to maintain these IP addresses. The client 202 then sends a request to connect to the subset port at the IP addresses, via step 402. When the client 202 receives a connect reply from one of the server systems, via step 403, it requests from the server system a list of server systems in the subset, via step 404. In this embodiment, the server system to which the client 202 is connected asks for this list from the system routing facility or table, and replies to the client 202 with the list, via step 405. Future connections between the client application and the subset will then be obtained using this server system list, via step 406.

For example, assume that client 202 wishes to send a request for an application whose work is to be performed by the “appgroup2” subset 204. The client 202 first obtains the IP addresses for the system servers of the “appgroup2” subset 204, via step 401. Assume that here, the DNS maintains these IP addresses, and that the IP address for server system 203.1 is “IP1”, and the IP address for server system 203.2 is “IP2”. “IP1” and “IP2” are thus returned to the client 202 from the DNS. The client 202 then sends a request to connect to port “9010” at “IP1” or “IP2”. If the client 202 does not receive a connect reply from “IP1” (or “IP2”), it sends the request to “IP2” (or “IP1”). Assume that the client 202 receives a connect reply from “IP1”, via step 403, connecting it to the server system 203.1. The client 202 then requests from server system 203.1 a list of server systems in the subset 204, via step 404. The server system 203.1 returns to the client 202 a list that contains itself and server system 203.2, via step 405. Future connections between the client 202 and the subset 204 will use this server list, via step 406.

For another example, assume that client 202 wishes to send a request for an application whose work is to be performed by the “appgroup3” subset 205. The client 202 first obtains the IP addresses for the system servers of the “appgroup3” subset 205, via step 401. Assume that here, the DNS maintains these IP addresses, and that the IP address for server system 203.5 is “IP5”, and the IP address for server system 203.6 is “IP6”. “IP5” and “IP6” are thus returned to the client 202 from the DNS. The client 202 then sends a request to connect to port “9020” at “IP5” or “IP6”. If the client 202 does not receive a connect reply from “IP5” (or “IP6”), it sends the request to “IP6” (or “IP5”). Assume that the client 202 receives a connect reply from “IP6”, via step 403, connecting it to the server system 203.6. The client 202 then requests from server system 203.6 a list of server systems in the subset 205, via step 404. The server system 203.6 returns to the client 202 a list that contains itself and server system 203.5, via step 405. Future connections between the client 202 and the subset 205 will use this server list, via step 406.

Although the above embodiment is described with a DNS, other means of routing the connection is possible. For example, if the group 201 has one IP address, a distributing router can be used to route the connection request to a particular subset of server systems based on the targeted port.

If the infrastructure of the group 201 supports workload balancing/routing, this feature is available for the subsets 204-205 as well. When a server system is activated, it registers itself with the workload balancer/router using the group name, as well as each subset name to which the server system is configured. When the server system is being accessed via its group name and port, it will request from the workload balancer/router the current list of server systems that are active in the group. If the server system is being accessed via one of its subset names and ports, then the server system will request from the workload balancer/router the current list of server systems that are active in the subset. This information is formatted and returned to the client 202. This information can also be server weighted so that the client 202, if made to use such information, can decide to which of the server systems future work is routed. Each time a client requests a new connection, or a reuse of a connection with a new user, an updated server list is returned.

When server systems leave the group, either through reconfiguration of the group or from failure, the information that was registered with the group workload balancer/router and/or request distributor for the server system is deregistered. In the case of abnormal server failures, the failing server system information is removed from the workload balancer/router and/or request distributor. Since the client has the information for available server systems, it can route work to the remaining server systems in the list.

An improved method and system of subsetting a group of server systems has been disclosed. The method and system configures a server system with a group name and a group port, and with a subset name and a subset port of at least one subset of the server systems in the group. The server system, when activated, reads its configuration and registers with a system routing entity as being part of the group name and the port, and as being part of the subset name and the subset port. In this manner, server systems can be targeted via its subset name and subset port, while also accessible via the common name and port for the group. Work can be targeted to certain subsetted server systems, while direct data sharing between the server systems of the group is maintained. In addition, if the group includes a workload balancer, the server system also registers with the workload balancer using the group name and the subset name. Workload balancing is thus provided for the subset as well as the group.

Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims. 

1. A method of subsetting a group comprising a plurality of server systems, comprising: configuring a server system of the plurality of server systems with a group name and a group port; configuring the server system with a subset name and a subset part of at least one subset of the plurality of server systems in the group; registering the server system with a system routing entity as being part of the group name and the group port; and registering the server system with the system routing entity as being part of the subset name and the subset port.
 2. The method of claim 1, further comprising: listening for connections on the group port and the subset port by the server system.
 3. The method of claim 2, further comprising: receiving a request to connect at the subset port from a client application; sending a connect reply to the client application; receiving a request from the client application for a list of server systems in the subset; obtaining the list from the system routing entity; and sending the list to the client application.
 4. The method of claim 3, wherein future connections between the client application and the subset utilizes the list.
 5. The method of claim 1, further comprising: registering the server system with a workload balancer of the group using the group name and the subset name.
 6. The method of claim 5, wherein when the server system is accessed through the group name and the group port, the server system obtains from the workload balancer a list of server systems active in the group.
 7. The method of claim 5, wherein when the server system is accessed through the subset name and the subset port, the server system obtains from the workload balancer a list of server systems active in the subset.
 8. A computer readable medium with program instructions for subsetting a group comprising a plurality of server systems, comprising the instructions for: configuring a server system of the plurality of server systems with a group name and a group port; configuring the server system with a subset name and a subset part of at least one subset of the plurality of server systems in the group; registering the server system with a system routing entity as being part of the group name and the group port; and registering the server system with the system routing entity as being part of the subset name and the subset port.
 9. The medium of claim 8, further comprising instructions for: listening for connections on the group port and the subset port by the server system.
 10. The medium of claim 9, further comprising instructions for: receiving a request to connect at the subset port from a client application; sending a connect reply to the client application; receiving a request from the client application for a list of server systems in the subset; obtaining the list from the system routing entity; and sending the list to the client application.
 11. The medium of claim 10, wherein future connections between the client application and the subset utilizes the list.
 12. The medium of claim 8, further comprising instructions for: registering the server system with a workload balancer of the group using the group name and the subset name.
 13. The medium of claim 12, wherein when the server system is accessed through the group name and the group port, the server system obtains from the workload balancer a list of server systems active in the group.
 14. The medium of claim 12, wherein when the server system is accessed through the subset name and the subset port, the server system obtains from the workload balancer a list of server systems active in the subset.
 15. A system, comprising: a system routing entity; and a group comprising a plurality of server systems, wherein a server system of the plurality of server systems is configured with a group name and a group port, wherein the server system is configured with a subset name and a subset port of at least one subset of the plurality of server systems in the group, wherein the server system is registered with the system routing entity as being part of the group name and the group port, and wherein the server system is registered with the system routing entity as being part of the subset name and the subset port.
 16. The system of claim 15, wherein the server system listens for connections on the group port and the subset port.
 17. The system of claim 15, further comprising a workload balancer, wherein the server system registers with the workload balancer using the group name and the subset name.
 18. The system of claim 17, wherein when the server system is accessed via the group name and the group port, the server system obtains from the workload balancer a list of server systems active in the group.
 19. The system of claim 17, wherein when the server system is accessed through the subset name and the subset port, the server system obtains from the workload balancer a list of server systems active in the subset. 